Skip to content

Migrate SLO workflows to Action v3 - #680

Draft
KirillKurdyukov wants to merge 3 commits into
mainfrom
ci/slo-v3-20261021
Draft

KirillKurdyukov wants to merge 3 commits into
mainfrom
ci/slo-v3-20261021

Conversation

@KirillKurdyukov

@KirillKurdyukov KirillKurdyukov commented Oct 21, 2026 •

Copy link
Copy Markdown

Summary

  • Run standalone and userver Table/Topic workloads with Action v3.
  • Select table for both KV workloads and topic for both Topic workloads. Retain the existing metrics, thresholds, commands, 600-second duration, and independent baseline SDK build with the shared workload harness.
  • Publish failed-run diagnostics through the v3 report action and let the action clean up the SLO label.

Dependency

Legacy telemetry compatibility is pinned to d66bd1e10f893e5f70d542c4430a3cffb6d6f9f8 from ydb-platform/ydb-slo-action#81 until that change is merged into v3. No SDK source, retries, deadlines, or workload scenarios are changed.

Earlier SDK verification

  • actionlint passed for both changed workflows.
  • git diff --check passed.
  • Final native four-workload SLO passed; automatic reports and SLO label cleanup are verified below.

Current workload metric contract

Use only existing workload sdk.* counters and successful-operation latency Gauges. workload_type selects table (default), topic, or topic_tx; it does not select a metric format. No SDK convention instruments or native/legacy schema split are supported by this change.

Init pins Action PR81 at immutable d66bd1e10f893e5f70d542c4430a3cffb6d6f9f8. Table retains independently built current/baseline SDKs and requires successful read AND write observations for both refs. Topic requires read/write and Topic-tx transaction observations, including any supplied baseline. Existing actual scenario names, SDK source, metrics YAML, retries, deadlines, load, data checks and fatal process criteria are unchanged.

The selector/pin changes pass actionlint across all seven SDK workflows. Action has135/135 Linux tests, clean static checks/bundle, public exact-SHA verify, independent gate approval and real SDK/OTLP PASS/FAIL/INVALID evidence. These are not a claim that historical native SDK runtime failures were fixed or that new SDK CI is green.

All PRs remain draft; no merge, ready transition or v3 tag move. Default-branch publisher changes are not active merely because this branch was pushed.

Related migration PRs

@codecov

codecov Bot commented Oct 21, 2026 •

Copy link
Copy Markdown

Codecov Report

✅ All modified and coverable lines are covered by tests.
✅ Project coverage is 56.81%. Comparing base (e1ecfaa) to head (3888837).

Additional details and impacted files
@@           Coverage Diff           @@
##             main     #680   +/-   ##
=======================================
  Coverage   56.80%   56.81%           
=======================================
  Files         290      290           
  Lines       33643    33643           
=======================================
+ Hits        19112    19114    +2     
+ Misses      14531    14529    -2     
Flag Coverage Δ
sdk 56.81% <ø> (+<0.01%) ⬆️

Flags with carried forward coverage won't be shown. Click here to find out more.

☔ View full report in Codecov by Harness.
📢 Have feedback on the report? Share it here.

🚀 New features to boost your workflow:
  • ❄️ Test Analytics: Detect flaky tests, report on failures, and find test suite problems.

@github-actions

Copy link
Copy Markdown
Contributor

🌋 SLO Test Results

🟢 4 workload(s) tested — All thresholds passed

Commit: 12691b0 · View run

Workload Thresholds Duration Report
cpp-key-value-userver 🟢 OK 10m 2s 📄 Report
cpp-topic 🟢 OK 10m 1s 📄 Report
cpp-key-value 🟢 OK 10m 3s 📄 Report
cpp-topic-userver 🟢 OK 10m 1s 📄 Report

Generated by ydb-slo-action

@github-actions github-actions Bot removed the SLO label Oct 21, 2026

This branch has not been deployed

No deployments
Sign up for free to join this conversation on GitHub. Already have an account? Sign in to comment

Labels

None yet

Projects

None yet

Development

Successfully merging this pull request may close these issues.

1 participant